Systems and methods for software provisioning in multiple network configuration environment

ABSTRACT

Embodiments relate to systems and methods for provisioning software to machines in a set of diverse networks. A provisioning (or “cobbler”) server can interact with a remote installation client to initiate a software provisioning process to machines installed on two or more diverse networks, such as local area, wide area, virtual private, or other networks. The remote installation clients in different networks can report the network interface types and configurations of their networks to the cobbler server. During provisioning, the administrator can specify one software distribution to the entire set of diverse networks, and the cobbler server can generate different distribution versions tailored to the network configurations of the various different networks. In embodiments, the cobbler server can maintain a set of network configuration templates to automatically set network settings such as static IP addresses, gateway information, hostname information, network mask information, and other settings for the different network types.

FIELD

The present teachings relate to systems and methods for softwareprovisioning in a multiple network configuration environment, and moreparticularly to platforms and techniques generating and installingsoftware installations to machines that may reside in a diverse networkenvironment having different interfaces or standards.

BACKGROUND OF RELATED ART

Provisioning platforms are known which allow a systems administrator toselect, configure, and push a set of software to new machines on anetwork. It is a shortcoming in existing provisioning platforms that thesystems administrator may have to know beforehand the type of networkinterface or configuration in which the target machines are intended tooperate, in order to set up the distribution. For example, the systemsadministrator may need to be aware that a given distribution is intendedto be installed on a set of machines that are connected via an EthernetLAN (local area network) in which each machine is running a certainversion of the Unix™ operating system, in order to select a distributiontemplate compatible with that network environment.

When faced with an installation project where the target network type orinterface is unknown, or in which two or more heterogeneous networkswill be present, conventional distribution platforms may be unable toperform an installation to all machines in that unknown or diverseenvironment.

It may be desirable to provide methods and systems for softwareprovisioning in a multiple network interface environment, in which thedistribution logic can detect and/or process diverse network types andautomatically deliver properly configured software versions to thedifferent network types, without a need for a systems administrator tomanually perform or configure the installation for each separate networkone by one.

DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments of the presentteachings and together with the description, serve to explain theprinciples of the present teachings. In the figures:

FIG. 1 illustrates an overall system for software provisioning in amultiple network configuration environment, according to variousembodiments of the present teachings;

FIG. 2 illustrates an overall system for software provisioning in amultiple network configuration environment, including identification ordiscrimination of different network configuration types to allowdifferentiation of distribution images based on network interface types,according to various embodiments;

FIG. 3 illustrates an exemplary hardware configuration for aprovisioning server and related resources that can be used to configureand install software packages in a network, according to variousembodiments; and

FIG. 4 illustrates a flowchart of overall processing for softwareprovisioning in a multiple network configuration environment, accordingto various embodiments.

DESCRIPTION OF EMBODIMENTS

Embodiments of the present teachings relate to systems and methods forsoftware provisioning in multiple network environments. Moreparticularly, embodiments relate to platforms and techniques forsoftware provisioning in multiple network environments, in whichsoftware images can be generated and deployed to a set of diverse orheterogeneous networks in an integrated installation process. Inembodiments, a remote installation client can host a network enginewhich can manage the deployment of versions of the software distributionthat are tailored to specific network types and configurations. Inembodiments, the network management engine can receive inputs for theuser indicating types of network configuration profiles to install onrespective network types. In embodiments, the network management enginecan in addition or instead perform a discovery process to automaticallydetect the types and configurations of the target networks for thesoftware distribution, and use templates for the respective networkinterfaces to generate network-specific installations. The softwareprovisioning can be carried out at times other than during a kickstartprocess. These and other embodiments described herein address thevarious noted shortcomings in known provisioning technology, and providea network operator or other user with enhanced provisioning capability,without a need to manually inspect, assign and/or configure networkinterface types to various versions of the distribution, and/or repeatthe installation process for each network interface type.

Reference will now be made in detail to exemplary embodiments of thepresent teachings, which are illustrated in the accompanying drawings.Where possible the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

FIG. 1 illustrates an overall provisioning environment 100 consistentwith systems and methods for storage allocation in the provisioning ofvirtual machines, according to various embodiments of the presentteachings. Embodiments described herein can be implemented in orsupported by the exemplary environment illustrated in FIG. 1. Theprovisioning environment 100 provides a unified provisioningenvironment, which comprehensively manages the tasks related to softwareprovisioning.

In particular, the provisioning environment 100 can manage softwareprovisioning using a hierarchy of commands. In exemplary embodiments,the hierarchy can include at least four levels of commands. The lowestlevel in the hierarchy can comprise distribution commands, whichprimarily handle base operating system specific tasks of provisioning.The second level can comprise profile commands, which associate aconfiguration file, such as a kickstart file for Linux or otheroperating system, with a distribution and optionally allow forcustomization. The third level comprises system commands, whichassociate remote systems that are involved with the provisioning of thesoftware. The fourth level comprises repository commands, which addressconfigurations and tasks related to updating the software, remoteinstallation procedures, and optionally customizing the software.

The provisioning environment 100 provides several capabilities andadvantages over the known provisioning solutions. For example, thepresent invention is capable of handling a variety of forms ofinstallations, such as preboot execution environment (“PXE”),virtualization, re-installations, and image installations.

In exemplary aspects, the provisioning environment 100 enablesintegrating virtualization into a PXE provisioning infrastructure andprovides several options to reinstall running machines as well. Theprovisioning environment 100 can integrate mirroring of packagerepositories with the provisioning process, so that a provisioningserver may serve as a central mirror point of contract for all of anorganization's software needs. In aspects, a set of remote mirroredrepositories can automatically be used by provisioned systems withoutadditional setup.

Reference will now be made in detail to the exemplary aspects theprovisioning environment 100. The provisioning environment 100 can beapplied to provisioning any form of software, such as Windows systems,UNIX systems, and Linux systems. In the exemplary description thatfollows, FIG. 1 is presented to explain the provisioning environment 100for provisioning software, such as Linux, and Linux based software, suchas Fedora and Red Hat Enterprise Linux by Red Hat, Inc.

In provisioning of software such as Linux, many system administratorsuse what is known as the “kickstart” installation method. Kickstartfiles are files that specify the intended configuration of the softwarebeing provisioned. Kickstart files can be kept on a server and can beread by individual computers during the installation. This installationmethod allows the use a single or relatively few standard kickstartfiles to install Linux on multiple machines, making it ideal for networkand system administrators.

The kickstart file can be a simple text file, containing a list ofitems, each identified by a keyword. In general, a kickstart file can beedited with any text editor or word processor that can save files asASCII text. One skilled in the art will recognize that the presentinvention may be applied to non-kickstart files in softwareprovisioning. For example, configuration files such as AutoYAST Answerfiles used in Novell SuSe Linux and Sun Solaris Jumpstart files may alsobe used by the provisioning environment 100.

Typically, a kickstart file can be copied to the boot disk, or madeavailable on the network. The network-based approach is most commonlyused, as most kickstart installations for software provisioning, such asLinux systems, tend to be performed via a network using NFS, FTP, orHTTP on networked computers. Administrators also find it desirable thatkickstart installations can be performed using a local CD-ROM, or alocal hard drive.

Using kickstart files, a system administrator can create a single filecontaining the parameters that are needed to complete a typical softwareinstallation. For example, kickstart files specify parameters relatedto: language selection; mouse configuration; keyboard selection; bootloader installation; disk partitioning; network configuration; NIS,LDAP, Kerberos, Hesiod, and Samba authentication; firewallconfiguration; and package selection.

According to exemplary aspects illustrated in FIG. 1, the provisioningenvironment 100 can include a provisioning server 102, a code repository104 which provides access to distributions 106 and 108, a set ofinstallation templates 110, a set of exception plugins 112, a helperclient 114 running on target machines 116 in a network 115, aprovisioning database 120 which comprises a distribution tree list 122and template list 124. Each of these components will now be furtherdescribed.

The provisioning server (from herein referred to as a “cobbler”) 102 isresponsible for: serving as a extensible markup language remoteprocedure call (XMLRPC) handler; linking to or mirroring installdistribution trees and a configuration database; hosting kickstarttemplates; hosting plugins, generating installation images, and thelike. The cobbler server 102 can be implemented as software, such asPython code, installed on a boot server machine and provides a commandline interface for configuration of the boot server. In addition, thecobbler server 102 can make itself available as a Python applicationprogramming interface (API) for use by higher level management software(not shown). The cobbler server 102 supports provisioning via PXE, image(ISO) installation, virtualization, reprovisioning. As will be describedlater, the last two modes are performed with the assistance of a helperclient 114.

The code repository 104 is responsible for hosting distributions 106 and108. The code repository 104 may be implemented using well knowncomponents of hardware and software. Additionally, the code repository104 can be or include one or more repositories hosting distributions.The distributions 106 and 108 can include bundles of software that isalready compiled and configured. The distributions 106 and 108 may be inthe form of either rpm, deb, tgz, msi, exe formats, and the like. Forexample, as Linux distributions, the distributions 106 and 108 arebundles of software that comprise the Linux kernel, the non-kernel partsof the operating system, and assorted other software. The distributions106 and 108 can take a variety of forms, from fully-featured desktop andserver operating systems to minimal environments.

In exemplary aspects, the installation templates 110 are any datastructure or processing element that can be combined with a set ofinstallation configurations and processed to produce a resultingconfiguration file, such as a kickstart file.

In exemplary aspects, exception plugins 112 is software that interactswith cobbler server 102 to customize the provisioning of software. Ingeneral, the exceptions plugins 112 are intended to address infrequentcustomization needs.

In exemplary aspects, the helper client (known as “koan”, which standsfor “kickstart-over-a-network”) 114 can assist the cobbler server 102during the provisioning processes. The koan 114 can allow for bothnetwork provisioning of new virtualized guests and destructiveprovisioning of any existing system. When invoked, the koan 114 canrequest profile information from a remote boot server that has beenconfigured with the cobbler server 102. In some aspects, what the koan114 does with the profile data depends on whether it was invoked with--virt or -replace-self.

In exemplary aspects, the koan 114 can enable replacing running systemsas well as installing virtualized profiles. The koan 114 can also bepushed out to systems automatically from the boot server. In someaspects, the koan client 114 is also written in Python code toaccommodate a variety of operating systems, machine architectures, etc.

In exemplary aspects, the network 115 can include a number of the targetmachines 116. The target machines 116 can represent the particularmachines to which software provisioning is directed. The target machines116 may represent a wide variety of computing devices, such as personalcomputers, servers, laptop computers, personal mobile devices, and thelike. In some aspects, the target machines 116 can represent distributedcomputing environments such as cloud computing environments. AlthoughFIG. 1 shows several of the target machines 116, the provisioningenvironment 100 can be capable of managing a wide range of environments,such as datacenters with thousands of machines or server pools with justa few machines. Additionally, the cobbler server 102 can be connected tomultiple networks 115.

In exemplary aspects, the provisioning database 120 can serve as a datastorage location for holding data used by the cobbler server 102. Forexample, as shown, the provisioning database 120 can comprise thedistribution tree list 122 and the template list 124. The distributiontree list 122 can provide an inventory of the distributions 106 and 108that are hosted or mirrored by the cobbler server 102. The template list124 can provide an inventory of the templates 110 that are hosted by thecobbler server 102.

As noted above, the cobbler server 102 can manage provisioning using ahierarchical concept of distribution commands, profile commands, systemcommands, and repository commands. This framework enables the cobblerserver 102 to abstract the differences between multiple provisioningtypes (installation, reinstallation, and virtualization) and allowsinstallation of all three from a common platform. This hierarchy ofcommands also permits the cobbler server 102 to integrate softwarerepositories 126 with the provisioning process, thus allowing systems tobe configured as a mirror for software updates and third party contentas well as distribution content.

Distributions can contain information about base operating system tasks,such as what kernel and initial ramdisk (“initrd”) are used in theprovisioning, along with other information, such as required kernelparameters. Profiles associate one of the distributions 106 and 108 witha kickstart file and optionally customize it further, for example, usingplugins 112. Systems commands associate a hostname, IP, or MAC with adistribution and optionally customize the profile further. Repositoriescontain update information, such as yum mirror information that thecobbler server 102 uses to mirror repository 104. The cobbler server 102can also manage (generate) DHCP configuration files using the templates110.

In exemplary aspects, the cobbler server 102 can use a provisioningenvironment that is fully templated, allowing for kickstarts and PXEfiles to be customized by the user. The cobbler server 102 uses theconcept of “profiles” as an intermediate step between the operatingsystem and the installed system. A profile is a description of what asystem does rather than the software to be installed. For instance, aprofile might describe a virtual web server with X amount of RAM, Yamounts of disk space, running a Linux distribution Z, and with ananswer file W.

In exemplary aspects, the cobbler server 102 can provide a command lineinterface to configure a boot server in which it is installed. Forexample, the format of the cobbler server 102 commands can be generallyin the format of: cobbler command [subcommand] [--arg1=] [--arg2=].Thus, a user can specify various aspects of software provisioning via asingle interface, such as a command line interface or other knowninterface. Examples of exemplary cobbler commands can be found in U.S.patent application Ser. No. 11/763,315, U.S. Patent ApplicationPublication No. ______ and U.S. patent application Ser. No. 11/763,333,U.S. Patent Publication No. ______, the disclosures of which areincorporated herein, in their entirety, by reference.

According to exemplary aspects, a user can use various commands of theprovisioning environment 100 to specify distributions and install treeshosted by the code repository 104, such as a distribution from thedistributions 106 or 108. A user can add or import a distribution orimport it from installation media or an external network location.

According to exemplary aspects, in order to import a distribution, thecobbler server 102 can auto-add distributions and profiles from remotesources, whether this is an installation media (such as a DVD), an NFSpath, or an rsync mirror. When importing a rsync mirror, the cobblerserver 102 can try to detect the distribution type and automaticallyassign kickstarts. By default in some embodiments, the cobbler servercan provision by erasing the hard drive, setting up eth0 for DHCP, andusing a default password. If this is undesirable, an administrator mayedit the kickstart files in /etc/cobbler to do something else or changethe kickstart setting after the cobbler server 102 creates the profile.

According to exemplary aspects, a user may map profiles to thedistributions and map systems to the profiles using profile commands andsystems commands of the provisioning environment 100. A profileassociates a distribution to additional specialized options, such as akickstart automation file. In the cobbler server 102, profiles are theunit of provisioning and at least one profile exists for everydistribution to be provisioned. A profile might represent, for instance,a web server or desktop configuration.

According to exemplary aspects, a user can map systems to profiles usingsystem commands. Systems commands can assign a piece of hardware withcobbler server 102 to a profile. Systems can be defined by hostname,Internet Protocol (IP) address, or MAC address. When available, use ofthe MAC address to assign systems can be preferred.

According to exemplary aspects, the user can map repositories andprofiles using repository commands. Repository commands can addressconfigurations and tasks related to updating the software, remoteinstallation procedures, and optionally customizing the software. Theserepository commands can also specify mirroring of the provisionedsoftware to remote servers. Repository mirroring can allow the cobblerserver 102 to not only mirror/install the trees 106 and 108, but alsooptional packages, third party content, and updates. Mirroring can beuseful for faster, more up-to-date installations and faster updates, orproviding software on restricted networks. The cobbler server 102 canalso include other administrative features, such as allowing the user toview their provisioning configuration or information tracking the statusof a requested software installation.

According to exemplary aspects, a user can utilize commands to create aprovisioning infrastructure from a distribution mirror. Then a defaultPXE configuration is created, so that by default systems will PXE bootinto a fully automated install process for that distribution. Thedistribution mirror can be a network rsync mirror or a mounted DVDlocation.

According to exemplary aspects, the administrator uses a local kerneland initrd file (already downloaded), and shows how profiles would becreated using two different kickstarts—one for a web serverconfiguration and one for a database server. Then, a machine can beassigned to each profile.

According to exemplary aspects, a repo mirror can be set up for tworepositories, and create a profile that will auto install thoserepository configurations on provisioned systems using that profile.

According to exemplary aspects, in addition to normal provisioning, thecobbler server 102 can support yet another option, called “enchant”.Enchant takes a configuration that has already been defined and appliesit to a remote system that might not have the remote helper programinstalled. Users might want to use this command to replace a server thatis being repurposed, or when no PXE environment can be created. Thus,the enchant option allows the remote the koan client 114 to be executedremotely from the cobbler server 102.

According to aspects, if the cobbler server 102 is configured to mirrorcertain repositories, the cobbler server 102 can then be used toassociate profiles with those repositories. Systems installed underthose profiles can be auto configured to use these repository mirrors incommands and, if supported, these repositories can be leveraged. Thiscan be useful for a large install base, fast installation and upgradesfor systems are desired, or software not in a standard repository existsand provisioned systems are desired to know about that repository.

According to exemplary aspects, the cobbler server 102 may also keeptrack of the status of kickstarting machines. For example, the “cobblerstatus” will show when the cobbler server 102 thinks a machine startedkickstarting and when it last requested a file. This can be a desirableway to track machines that may have gone inactive during kickstarts. Thecobbler server 102 can also make a special request in the post sectionof the kickstart to signal when a machine is finished kickstarting.

According to exemplary aspects, for certain commands, the cobbler server102 will create new virtualized guests on a machine in accordance to theorders from the cobbler server 102. Once finished, an administrator mayuse additional commands on the guest or other operations. The cobblerserver 102 can automatically name domains based on their MAC addresses.For re-kickstarting, the cobbler server 102 can reprovision the system,deleting any current data and replacing it with the results of a networkinstall.

According to exemplary aspects, the cobbler server 102 can configureboot methods for the provisioning requested by the user. For example,the cobbler server 102 can configure a PXE environment, such as anetwork card BIOS. Alternatively, the cobbler server 102 can compile andconfigure information for koan client 104. The cobbler server 102 canalso optionally configured DHCP and DNS configuration information.

According to exemplary aspects, the cobbler server 102 can serve therequest of the koan client 114. The koan client 114 can acknowledge theservice of information of the cobbler server 102 and then can initiateinstallation of the software being provisioned. Additionally, the koanclient 114 can either install the requested software, e.g., replace theexisting operating system, or install a virtual machine.

FIG. 2 illustrates an overall network 100 consistent with systems andmethods for software provisioning in multiple network environments,according to various aspects of the present teachings in furtherregards. In embodiments as shown, a set of diverse networks 220 cancommunicate with cobbler server 102 to initiate a software provisioningor distribution process. The provisioning can be initiated by therequest of a systems administrator, or other user. The set of diversenetworks 220 can include a set of two or more diverse networkconfigurations or types, each with a set of targets 116 and one or moreremote installation clients 244 in each different or distinct networktype. Set of diverse networks 220 can contain or include, for example,any two or more of a personal area network, a local area network, ametropolitan area network, a wide area network, the Internet, anintranet, an extranet, a virtual private network, a peer-to-peernetwork, and a wireless self-configuring network. Other network typesare possible.

Each network type or category within set of diverse networks 220 canhave a different set of physical or media-level specifications orparameters, as well as other settings and configurations. Each networkcan have a separate or distinct set of interface and/or configurationparameters, including, for instance, static IP (Internet protocol)addresses or other information, gateway addresses or other information,hostname information, netmask information, and other network settings.Other network settings can further include port configuration settings,physical layer specification settings, data link layer specificationsettings, network layer specification settings, transport layerspecification settings, security or encryption settings, and userauthentication settings. Because the requirements and specifications foreach distinct network type may be different, cobbler server 102 may notbe able to generate identical distribution(s) 106, 108 to each networkin set of diverse networks 220. Instead, cobbler server 102 can generatea tailored or specific version of distribution(s) 106, 108 to respectivedifferent networks in set of diverse networks 220, depending onparticular requirements of each.

In embodiments, cobbler server 102 can access a set of installationtemplates 110 containing configuration details for each differentnetwork to be integrated into the various networks in set of diversenetworks 220. In embodiments, the systems administrator or other usercan specify or indicate different network types to be located within setof diverse networks 220. In embodiments, one or more network managementengine 224 hosted in the set of remote installation clients 244 can inaddition or instead perform an automatic detection or discovery process,to report the network configuration types/interface parameters for thedifferent networks in set of diverse networks 220 to cobbler server 102.In embodiments, the systems administrator or other user can view,update, override, or otherwise modify the network configurationparameters that are automatically detected or generated by the networkmanagement engine 224 of the remote installation clients 244. Inembodiments, the automatically detected network configuration/interfacedata can be used to initiate software provisioning, with no furthermodification or intervention.

When the set of installation templates 110 are generated, cobbler server102 can generate distributions(s) 106, 108 to the different networks inset of diverse networks 220 based on corresponding network interfaceparameters, and transmit those distributions to the different networksin set of diverse networks 220. Installation of the distribution canproceed via the remote installation clients 244 and network managementengine 224 located in each different network. In embodiments, thedistribution(s) 106, 108 can be or include an operating system,applications, or other software. When initial installation is complete,testing or verification of the installation can be performed via networkmanagement engine 224 and/or other logic. In embodiments, networkmanagement engine 224 or other resources can continue to monitor theconstituent networks of set of diverse networks after completion of thesoftware provisioning, for example to monitor for changes to networkconfiguration and report those changes to cobbler server 102 orotherwise. In embodiments in various regards, a systems administrator orother user therefore need not manually detect, configure, and/or assignnetwork configuration settings to individual sets of machines in diversenetworks as they are provisioned or updated.

FIG. 3 illustrates an exemplary diagram of hardware and other resourcesthat can be incorporated in the cobbler server 102 configured tocommunicate with the network 115 and the target machines 116 in network115, according to embodiments. In embodiments as shown, the cobblerserver 102 can comprise a processor 300 communicating with memory 302,such as electronic random access memory, operating under control of orin conjunction with operating system 306. Operating system 306 can be,for example, a distribution of the Linux™ operating system, the Unix™operating system, or other open-source or proprietary operating systemor platform. Processor 300 also communicates with the provisioningdatabase 120, such as a database stored on a local hard drive. Whileillustrated as a local database in the cobbler server 102, theprovisioning database 120 can be separate from the cobbler server 102and the cobbler server 102 can be configured to communicate with theremote provisioning database 120.

Processor 300 further communicates with network interface 304, such asan Ethernet or wireless data connection, which in turn communicates withone or more networks 115, such as the Internet or other public orprivate networks. Processor 300 also communicates with the provisioningdatabase 120, the network management engine 224 and other resources toexecute control logic and perform the storage allocation andprovisioning processes described herein. Other configurations of thecobbler server 102, associated network connections, and other hardwareand software resources are possible.

While FIG. 3 illustrates the cobbler server 102 as a standalone systemcomprising a combination of hardware and software, the cobbler server102 can also be implemented as a software application or program capableof being executed by a convention computer platform. Likewise, thecobbler server 102 can also be implemented as a software module orprogram module capable of being incorporated in other softwareapplications and programs. In either case, the cobbler server 102 can beimplemented in any type of conventional proprietary or open-sourcecomputer language.

FIG. 4 illustrates overall provisioning and storage allocationprocessing in systems and methods for software provisioning in multiplenetwork environments, according to various embodiments of the presentteachings. In 402, processing can begin. In 404, a request to initiate asoftware provisioning process on a set of diverse networks 220 can bereceived in cobbler server 102. In 406, input can be received from asystems administrator or other user for the specification of networktypes, configuration settings or other inputs or settings to be used inthe provisioning process, if any. In 408, the cobbler server 102 canreceive detected network interface types or other network configurationinformation automatically reported by the set of remote installationclients 244 in different networks of set of diverse networks 220, asappropriate. For instance, one or more remote installation client 244 inone or more different network of set of diverse networks 220 can captureand report a network type, such as a local area network, wide areanetwork, or other type of network and/or network interface to cobblerserver 102. In 410, the cobbler server 102 can generate a set ofinstallation templates 110 based on the received configurationinformation or other attributes of set of diverse networks 220.

In 412, cobbler server 102 can initiate the delivery of softwaredistributions 106, 108 to set of diverse networks 220 based on thegenerated set of installation templates 110 to respective differentnetworks in set of diverse networks 220. Thus, for example, one networkmay receive distribution(s) 106, 108 with software configured tocommunicate via port 1021 using TCP/IP (transport controlprotocol/Internet protocol), while another receive distribution(s) 106,108 with software configured to communicate via port 434 using ftp (filetransfer protocol). Other configurations can be used. In 414,distribution(s) 106, 108 can be installed to and/or verified on thedifferent networks of the set of diverse networks 220. In 416, cobblerserver 102 can receive additional post-installation settings from thesystems administrator or other user, as appropriate. In 418, theconfigurations and other data associated with the installeddistribution(s) 106, 108 provisioned to set of diverse networks 220 canbe recorded or stored to provisioning database 120 or otherwise. In 420,processing can repeat, return to a prior processing point, jump to afurther processing point, or end.

The foregoing description is illustrative, and variations inconfiguration and implementation may occur to persons skilled in theart. For example, while embodiments have been described in whichsoftware provisioning to set of diverse networks 220 can be generatedvia a single cobbler server 102, in embodiments multiple provisioning orcobbler servers can be used. For further example, while embodiments havebeen described in which different network types receive differentdistribution(s) 106, 108, in embodiments different networks can receivethe same version of distributions 106, 108, depending on possibleinter-network compatibilities or other factors. Other resourcesdescribed as singular or integrated can in embodiments be plural ordistributed, and resources described as multiple or distributed can inembodiments be combined. The scope of the present teachings isaccordingly intended to be limited only by the following claims.

1. A method of software provisioning in a multiple network environment,comprising: receiving a request for the initiation of at least onesoftware provisioning process on a set of diverse networks in aprovisioning server; communicating with at least one remote installationclient in each different network in the set of diverse networks toprovision software to the set of machines in each respective differentnetwork, each different network having a respective network interfacetype; and automatically generating a distribution configuration for eachdifferent network based on the network interface type for eachrespective different network.
 2. The method of claim 1, wherein the setof diverse networks comprises at least two of a personal area network, alocal area network, a metropolitan area network, a wide area network,the Internet, an intranet, an extranet, a virtual private network, apeer-to-peer network, and a wireless self-configuring network.
 3. Themethod of claim 1, wherein the distribution configuration is generatedvia a set of configuration templates, each configuration template beingassociated with a respective network interface type.
 4. The method ofclaim 3, wherein the set of configuration templates comprises at leastone of static IP (Internet protocol) information, gateway information,hostname information, netmask information, a port configuration setting,a physical layer specification setting, a data link layer specificationsetting, a network layer specification setting, a transport layerspecification setting, an encryption setting, and a user authenticationsetting.
 5. The method of claim 1, wherein the provisioned softwarecomprises at least one of operating system software and applicationsoftware.
 6. The method of claim 1, wherein the network interface typefor at least one of the diverse networks is configured via user input.7. The method of claim 1, wherein the network interface type for atleast one of the diverse networks in automatically configured via anautomatic detection process.
 8. A system for generating a softwaredistribution in a multiple network environment, comprising: an interfaceto a set of diverse networks, each different network in the set ofdiverse networks having at least one associated remote installationclient; and a provisioning server, communicating with the set of diversenetworks via the interface, the provisioning server being configured toreceive a request for the initiation of at least one softwareprovisioning process on the set of diverse networks, communicate with atleast one remote installation client in each different network in theset of diverse networks to provision software to the set of machines ineach respective different network, each different network having arespective network interface type, and automatically generate adistribution configuration for each different network based on thenetwork interface type for each respective different network.
 9. Thesystem of claim 8, wherein the set of diverse networks comprises atleast two of a personal area network, a local area network, ametropolitan area network, a wide area network, the Internet, anintranet, an extranet, a virtual private network, a peer-to-peernetwork, and a wireless self-configuring network.
 10. The system ofclaim 8, wherein the distribution configuration is generated via a setof configuration templates, each configuration template being associatedwith a respective network interface type.
 11. The system of claim 10,wherein the set of configuration templates comprises at least one ofstatic IP (Internet protocol) information, gateway information, hostnameinformation, netmask information, a port configuration setting, aphysical layer specification setting, a data link layer specificationsetting, a network layer specification setting, a transport layerspecification setting, an encryption setting, and a user authenticationsetting.
 12. The system of claim 8, wherein the provisioned softwarecomprises at least one of operating system software and applicationsoftware.
 13. The system of claim 8, wherein the network interface typefor at least one of the diverse networks is configured via user input.14. The system of claim 8, wherein the network interface type for atleast one of the diverse networks in automatically configured via anautomatic detection process.
 15. A set of diverse networks, the set ofdiverse networks being provisioned with software according to a methodcomprising: receiving a request for the initiation of at least onesoftware provisioning process on the set of diverse networks in aprovisioning server; communicating with at least one remote installationclient in each different network in the set of diverse networks toprovision software to the set of machines in each respective differentnetwork, each different network having a respective network interfacetype; and automatically generating a distribution configuration for eachdifferent network based on the network interface type for eachrespective different network.
 16. The set of diverse networks of claim15, wherein the set of diverse networks comprises at least two of apersonal area network, a local area network, a metropolitan areanetwork, a wide area network, the Internet, an intranet, an extranet, avirtual private network, a peer-to-peer network, and a wirelessself-configuring network.
 17. The set of diverse networks of claim 15,wherein the distribution configuration is generated via a set ofconfiguration templates, each configuration template being associatedwith a respective network interface type.
 18. The set of diversenetworks of claim 17, wherein the set of configuration templatescomprises at least one of static IP (Internet protocol) information,gateway information, hostname information, netmask information, a portconfiguration setting, a physical layer specification setting, a datalink layer specification setting, a network layer specification setting,a transport layer specification setting, an encryption setting, and auser authentication setting.
 19. The set of diverse networks of claim15, wherein the provisioned software comprises at least one of operatingsystem software and application software.
 20. The set of diversenetworks of claim 15, wherein the network interface type for at leastone of the diverse networks is configured via user input.
 21. The set ofdiverse networks of claim 15, wherein the network interface type for atleast one of the diverse networks in automatically configured via anautomatic detection process.